home *** CD-ROM | disk | FTP | other *** search
- From: ecd@cert.sei.cmu.edu (Edward DeHart)
- Newsgroups: comp.unix.admin
- Subject: Re: Cracked accounts
- Keywords: intruder security CERT
- Message-ID: <860@cert.sei.cmu.edu>
- Date: 29 Oct 91 05:18:13 GMT
- Organization: Computer Emergency Response Team, Pittsburgh, PA
-
-
- I have been following the discussions about closing an account and
- I am glad to see folks suggest changing the login shell to something
- that prints a messages and then exits. Too many sites just change the
- password. Just changing the password might not keep the user out of the
- account if your UNIX systems trust other UNIX systems via .rhosts files and
- the /etc/hosts.equiv file.
-
- I would like to address the problem of closing an account which has been
- broken into. In addition to locking or closing the account, I would like
- to suggest a few more steps to take.
-
- Please do not confine the examination of your system to just the locked
- account. We have found that too many system managers close the account
- used by the intruder and examine the files in just that account. If an
- intruder really did gain access to your system there is a good chance that
- the intruder has copied the /etc/passwd file from your system to another
- system. There are several password cracking programs that would allow
- the intruder to crack passwords on other accounts. To solve this problem
- you could either change the passwords on all accounts at one time and
- make sure that your users never use their old passwords or you could use
- one of the password breaking programs yourself. This will allow you to
- change the accounts with easy to guess passwords.
-
- When examining files on your system, please do not stop with just the files
- in the cracked account. Check the /etc/passwd file for uid changes or
- new accounts. Check the /etc/inetd.conf file for modifications such as
- the TFTP daemon being enabled or a service that executes /bin/sh or /bin/csh.
- To be on the safe side, reload the operating system binaries in /bin,
- /usr/bin, /usr/etc, /etc, and /usr/ucb (if you have this directory) from
- the vendor's distribution tape (not from a backup tape).
-
- My last suggestion is to contact us. We are able to provide additional
- information that could help you secure your system. The information
- gained by us from your experience could be an important part in a much
- larger puzzle.
-
- Thank you,
- Ed DeHart
- Computer Emergency Response Team
- Internet E-mail: cert@cert.sei.cmu.edu
- Telephone: 412-268-7090 24-hour hotline:
- CERT personnel answer 7:30a.m.-6:00p.m. EST, on call for
- emergencies during other hours.
-
-
-
-